Look for more instructions and modules from wherever you got this copy, or the MUBBS Support BBS.
The MUBBS Main Module is FreeWare. You can use it for free, but you can't sell it or use any of my included source code in a commercial or "ShareWare" product (you can charge for access to your BBS). You are limited by each module's author copyright file, please read them.
The MUBBS Main Module will always be FREE. This is my promise to you that I will keep it free. If I ever start starving and can't feed my family, I'll go around and set up BBS's for local companies that need them.
Please READ this documentation, this is not a normal Mac program !
About MUBBS:
MUBBS is a "Multi User BBS" and is modular.
MUBBS started out as a "hack" I put together to run my own BBS with. Several people showed a interest in it so I "cleaned" it up and am shipping it out.
You can program your own modules, then add them to MUBBS wherever you like. You can basically construct your own custom BBS any way you please.
MUBBS can handle up to 32 LINES (and eats lots of memory when doing so).
Source code for sample modules is available on the support BBS. Programmers of modules are encouraged to release their source code so that others can build "on top" of what they have done and then release the "improved upon" source.
The idea is that if everyone writes a module and releases it, you will get more and better modules in return !
Since each author of a module supports only a small amount of code (normally less then 32K), there isn't any "support hassles" involved. Support time may add up to 2 hours a month maximum, so most authors won't find it necessary to charge for a module.
Large modules like "super world info sorter" that take a lot of programming time my end up being "ShareWare" for MUBBS. Please pay any fees that authors ask for, you will get better modules in return.
MUBBS is meant to be run like a 24 Hr BBS. This means a SEPARATE computer turned on all the time. It's not meant to be used part time in the background of whatever word processing tasks you are doing. It runs fine under MultiFinder, but it's not necessary and you should use single finder and save your memory space.
It also works fine under System 7 and has been tested with the new Mac Portables. If you can run system 6.0.7 please do. It leaves you with more memory and 7 is really not needed.
The minimum configuration I will always shoot for is a Mac Plus with 1 Meg of RAM. The RAM is what may need increasing in the future.
It runs pretty good on a Plus, and Mac Plus's are running about $500 used currently. If you look around, you can always get a deal and set up your BBS properly. I really hate calling a BBS number and find that its not up because I called at the wrong time, or even worse; getting a voice on the line because it's a voice line during the day.
If you are going to be a Sysop, you need a way to log into your BBS from ELSEWHERE. The monitor screen is just that A MONITOR SCREEN. It's made so that you can locally log in because the Mac can do it, but you really need to see what your user's are seeing.
Old Terminals are about $10 each. No one wants them anymore, I see people at swap meets using them as seats and most of them would rather GIVE you one then have to LUG it home !
If you are NEW to BBSing, WELCOME! It will take sometime for you to use this program, it's NOT A STANDARD EASY TO USE MAC PROGRAM, nor was it ever intended to be. You are now crossing over into the "Sysop Zone" !
Configuration of Modules and other Accessories to MUBBS will be in the form of small APPLICATIONS because of system 7's way you can add applications to the "apple" menu. It was nice of Apple to think of us MUBBS users when they designed system 7 ! If you are using 6.0.7 it's no problem, they are still applications. (You don't use them WHILE people are online ! )
Being a Sysop:
You are about to become a Sysop !
This means operating a place for thousands (hundreds?) of people to check into. You are just ONE out of many that will have to put up with any "bad" set up you do.
MUBBS is NOT a normal "click and run" Mac program !!
You can set it up as you like, but that's not going to take 10 minutes. You need to spend some time thinking about how you would like your BBS to appear.
Your startup screen is just about the most important thing about the BBS. Make it LARGE and fill a whole screen. It's like a "first impression" for your BBS.
The EASE of operation is important too. MUBBS is very "User Friendly".
My advice is to run as open a system as you can, and don't worry if EVERYONE downloads. People will eventually UPLOAD when they see you run a open and "nice" system. I get people calling long distance at 1200 baud uploading stuff !
You need a type of "Unverified Uploads" section that even first callers have access to. Leaving GIF and TEXT fie sections open is OK because you can't put a virus in a STRAIGHT TEXT or GIF file.
The reason for this is that there's lots of NEW and good information that you will get from people that call long distance to distribute their TEXT files. If they have to be called back, or have to call back again it probably won't happen.
Talk to other Sysop's ! They have seen it all and their input is valuable.
Some quick details:
Make sure all INITs are off, get rid of those pesky CDEVs that arn't standard too. You don't need a million INIT's when running a BBS. IF YOU HAVE INITS IN AND ARE HAVING PROBLEMS, DON'T BOTHER REPORTING YOUR PROBLEMS (you're just wasting your and other people's time)!!!!!
MUBBS is set up to pick up the line, wait for carrier detect switch baud rates and then call the first module.
You NEED a TEXT editor (MacWrite sucks for this) to edit configuration files in MUBBS. JolliWrite is a GREAT DA that does this nicely, and it even runs all the way up to a Fx.
EACH MODULE HAS IT'S *OWN* INSTRUCTION FILE, please read them.
The first module called is "maincaller", a "caller" type module. A "caller" type module calls other modules from a TEXT file list of modules to call. The modules to be called are in the "caller" folder. They are named the same as the module with ".info".
MAKE SURE YOU INCLUDE A (CR) after each name, and DON'T add extra (CR)'s in the file (one after each name only).
In this archive, "maincaller" is set to call a "sendfile" module (called "sendfile1") that sends "systemstartup.txt" then the "login" module then a "menu" module (called "menu1").
"menu1" then calls all sorts of EXAMPLE modules and the File and E-mail modules. You need to look at the instructions for each EXAMPLE module to figure out what they are doing, you may go CRAZY wondering why the "start" text is being sent again. Remember, any module can be called anytime ! (by your command).
You can configure MUBBS to do whatever you want it to !
Don't expect to pick all this up immediately, it's gona take some time to figure out what I'm doing. I can't explain it all here, and I will be putting together some more text for you soon.
LEAVE ALL FOLDERS ALONE ! DON'T RENAME THEM and DON'T RENAME MUBBS !
You can rename the "MUBBS Vx.x" FOLDER to whatever you want (the folder MUBBS came in hopefully).
You install new modules by using "ResEdit 2.x". ResEdit 2.0 and above allow you to do a "unique ID" when there is already a module that has a ID that your's does. MUBBS doesn't care about ID numbers, just names. You just copy and paste modules like any other Mac program.
Use "get resource info" to change the module's name and or ID number as you wish.
There may be a "installer" later that does all this for you, but for now use resedit.
If you need two "menu" modules for two different menus, name one "menu1" and the other "menu2". Your configuration files will need to be made in the "menus" folder under the names "menu1.info" and "menu2.info". You get the idea...
The modules depend on folders being names a certain way.
Most MUBBS configuration TEXT files allow for about 30 characters MAX on a line. That's why it's important that you keep your lines short and make sure to include the PROPER data. Checking the line lengths takes processor and programming time, so you should check it YOURSELF.
The modem strings are in the "bbsconfig" file under "modems".
It is ready to go as is, MUBBS runs on a Mac plus with 1 meg and ONE serial port. Use modem cables that give CARRIER DETECT back to the computer. IT IS LOOKING FOR A MODEM ON THE "MODEM" PORT! If you don't a modem on the port it will be slow while it looks for the modem ! (see the last few paragraphs for logging in on a terminal).
I HIGHLY RECOMMEND GETTING A CARRIER DETECT MODEM CABLE !! This is a standard modem cable most of the time. If you're not sure, use a "ohm" meter and check your pins against the "modem cable" file.
MUBBS has the basics that are important to any BBS, and they are working very well. Handling the serial ports seems like a easy task for those who don't program, but that is one of the hardest things to do. Switching between two users, all the while using the SAME code is also not a simple task. A lot of thought has been put into the Main Module's code.
MUBBS is set up to run on a Mac Plus with 1 meg ram because you can buy 512 boards cheap and hack together a plus for under $400. It should run on other configurations, but don't complain too loud when it doesn't.
If you are going to run two lines, you need 2 megs.
The best way to learn is to run the BBS and play around with it...
When I originally designed MUBBS it was made so that I could do almost everything from a remote location. There isn't much of a Mac interface. You cannot actually see what a user is doing because the MAC'S scrolling SLOWS the system down considerably. There are reports in each window that show where the user is, and what he is selecting. I would think later there would be a option to monitor a port for a while, and if you leave it alone it automatically switches back. This would allow the system to operate at it's highest efficiency.
